User Entity Schema by artemdemo · Pull Request #406 · base44/cli

artemdemo · 2026-03-11T14:35:13Z

Note

Description

This PR adds local User entity support to the base44 dev server, replacing the previous behavior of proxying all /User requests to production. The current authenticated user is automatically seeded into an in-memory User collection on startup, and a new JWT-aware router handles CRUD operations for the User entity locally. Entity names are now normalized to lowercase for consistent lookup.

Related Issue

None

Type of Change

Bug fix (non-breaking change which fixes an issue)
New feature (non-breaking change which adds functionality)
Breaking change (fix or feature that would cause existing functionality to not work as expected)
Documentation update
Refactoring (no functional changes)
Other (please describe):

Changes Made

Added a dedicated entities-user-router.ts that handles GET /User/:id (including me), POST /User/, PUT /User/:id with JWT-based auth via a withAuth wrapper
Database.load() is now async and automatically seeds a User collection with the current authenticated user's info (from readAuth())
Added buildUserSchema() to merge built-in User fields (full_name, email) with any custom User entity schema, and validates that built-in fields are not overridden
Refactored entities.ts → routes/entities/entities-router.ts and removed the remoteProxy parameter (no longer needed for User routes)
Moved stripInternalFields utility to utils.ts and entity name normalization (.toLowerCase()) added to Database
Changed Validator to throw EntityValidationError instead of returning a validation response object; callers updated to catch and return HTTP 422
Added jsonwebtoken dependency for decoding Bearer tokens in the local dev server
Updated validator tests to match the new throw-based validation API

Testing

I have tested these changes locally
I have added/updated tests as needed
All tests pass (npm test)

Checklist

My code follows the project's style guidelines
I have performed a self-review of my own code
I have commented my code, particularly in hard-to-understand areas
I have made corresponding changes to the documentation (if applicable)
My changes generate no new warnings
I have updated docs/ (AGENTS.md) if I made architectural changes

Additional Notes

The User collection is pre-populated with the logged-in developer's info (email, name, role=admin) so that local apps behave similarly to production when reading the current user. Restricted fields (full_name, email, role) cannot be updated via the entities API, mirroring production backend constraints. The POST /User/bulk endpoint is a no-op, consistent with production behavior.

_{🤖 Generated by Claude | 2026-03-22 00:00 UTC}

github-actions · 2026-03-11T14:35:49Z

🚀 Package Preview Available!

Install this PR's preview build with npm:

npm i @base44-preview/cli@0.0.47-pr.406.4b9c508

Prefer not to change any import paths? Install using npm alias so your code still imports base44:

npm i "base44@npm:@base44-preview/cli@0.0.47-pr.406.4b9c508"

Or add it to your package.json dependencies:

{
  "dependencies": {
    "base44": "npm:@base44-preview/cli@0.0.47-pr.406.4b9c508"
  }
}

📦 Preview Package: @base44-preview/cli@0.0.47-pr.406.4b9c508
🔗 View this commit on GitHub

_{Preview published to npm registry — try new features instantly!}

artemdemo · 2026-03-18T07:15:04Z

packages/cli/src/cli/utils/command/Base44Command.ts

  /** @public - called by Commander internally via command dispatch */
  override action(
    // biome-ignore lint/suspicious/noExplicitAny: must match Commander.js action() signature
+    // biome-ignore lint/suspicious/noConfusingVoidType: must match Commander.js action() signature


Not related to my PR, but started to fail for me.
Ignoring

artemdemo · 2026-03-18T07:15:58Z

packages/cli/tests/scripts/validator.spec.ts

-      const result = validator.validate({ name: "Alice" }, schema);
-
-      expect(result.hasError).toBe(false);
+      expect(() => validator.validate({ name: "Alice" }, schema)).not.toThrow();


Validator is now throwing an error, instead of returning object that describes the error.
Updating tests to handle it.
Here and below.

artemdemo · 2026-03-18T07:16:56Z

packages/cli/src/cli/dev/dev-server/db/validator.ts

      );
      if (requiredFieldsResponse.hasError) {
-        return requiredFieldsResponse;
+        throw new EntityValidationError(requiredFieldsResponse.error);


I found that it's more convenient to throw the error, rather than return an object that describes the error.
So I decided to refactor it a bit.

artemdemo · 2026-03-18T12:47:51Z

packages/cli/src/cli/dev/dev-server/db/database.ts

+  private normalizeName(entityName: string): string {
+    return entityName.toLowerCase();
+  }


Behind the scenes production is treating entity name as case-insensitive: "User" and "user" are the same.

kfirstri

Looks good, i'm not sure i understand some stuff in the entities-user-router..
Also, can we resolve the user with the auth token and not with readAuth somehow? I see we added a check to assert the api calls has a Bearer.. so maybe we can parse the token?

packages/cli/src/cli/dev/dev-server/main.ts

packages/cli/src/cli/dev/dev-server/routes/entities/entities-user-router.ts

kfirstri · 2026-03-19T16:39:24Z

packages/cli/src/cli/dev/dev-server/routes/entities/entities-user-router.ts

+            return;
+          }
+          logger.error(
+            `Error in PUT /${USER_COLLECTION}/${req.params.id}:`,


This error looks weird, no need to use USER_COLLECTION inside the url that we're printing

Why? Can you elaborate, what is weird about it?
Can you give example of an error that you have in mind?

It's probably fine for now, but i mean that it's just a coincidence that the endpoint route /users/:id has the same name as the collection, the collection name can be "users_collection", but the route will remain "users/"

packages/cli/src/cli/dev/dev-server/routes/entities/entities-user-router.ts

packages/cli/src/cli/dev/dev-server/db/database.ts

kfirstri · 2026-03-23T08:44:43Z

packages/cli/src/cli/dev/dev-server/routes/entities/entities-user-router.ts

+  const router = createRouter({ mergeParams: true });
+  const parseBody = json();
+
+  function withAuth<R>(


kfirstri

noice

artemdemo force-pushed the users-and-auth branch from 04e8a12 to f8afa4a Compare March 15, 2026 14:54

artemdemo changed the title ~~Users and Authorization~~ Users Schema Mar 16, 2026

artemdemo force-pushed the users-and-auth branch 2 times, most recently from 11c2912 to f7b1fa4 Compare March 17, 2026 16:06

artemdemo commented Mar 18, 2026

View reviewed changes

base44 deleted a comment from claude bot Mar 18, 2026

artemdemo force-pushed the users-and-auth branch from 44675f2 to 2d12f4c Compare March 18, 2026 12:44

artemdemo changed the title ~~Users Schema~~ Users Entity Schema Mar 18, 2026

artemdemo changed the title ~~Users Entity Schema~~ User Entity Schema Mar 18, 2026

artemdemo commented Mar 18, 2026

View reviewed changes

base44 deleted a comment from claude bot Mar 18, 2026

User Entity

db4c86f

artemdemo marked this pull request as ready for review March 18, 2026 12:50

kfirstri added this to CLI Development Mar 18, 2026

github-project-automation bot moved this to Backlog in CLI Development Mar 18, 2026

kfirstri moved this from Backlog to In review in CLI Development Mar 18, 2026

kfirstri self-requested a review March 19, 2026 15:31

kfirstri requested changes Mar 19, 2026

View reviewed changes

github-project-automation bot moved this from In review to Ready in CLI Development Mar 19, 2026

artemdemo added 3 commits March 22, 2026 14:09

restrict fields

8937312

upd

32d78cb

moved check for authorization

3439aa4

artemdemo force-pushed the users-and-auth branch from 2d12f4c to 3439aa4 Compare March 22, 2026 13:35

upd

5ff7d9e

kfirstri reviewed Mar 23, 2026

View reviewed changes

kfirstri approved these changes Mar 23, 2026

View reviewed changes

github-project-automation bot moved this from Ready to In review in CLI Development Mar 23, 2026

artemdemo merged commit 09cae17 into main Mar 23, 2026
23 checks passed

github-project-automation bot moved this from In review to Done in CLI Development Mar 23, 2026

artemdemo deleted the users-and-auth branch March 23, 2026 08:51

Conversation

artemdemo commented Mar 11, 2026 • edited by claude bot Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Description

Related Issue

Type of Change

Changes Made

Testing

Checklist

Additional Notes

Uh oh!

github-actions bot commented Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

🚀 Package Preview Available!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kfirstri left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

Uh oh!

Choose a reason for hiding this comment

Uh oh!

kfirstri left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

2 participants

artemdemo commented Mar 11, 2026 •

edited by claude bot

Loading

github-actions bot commented Mar 11, 2026 •

edited

Loading